docs(detection): fix mismatched backticks for mmsegmentation in README#326
Open
MukundaKatta wants to merge 1 commit intoOpenGVLab:masterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
detection/README.mdline 54 has a quote/backtick mismatch for `mmsegmentation`:Before:
```
```
After:
```
```
The leading backtick was escaped (`\``) and closed with a single quote, so Markdown rendered it as literal \` text instead of inline code. Matched with a real backtick on both sides so it renders consistently with the other package names on the same line.
Closes #325
Testing
Documentation-only change; no code paths touched. Verified the surrounding section renders with consistent inline-code formatting.